netif.h: describe request/response structures in terms of binary layout
authorIan Campbell <ian.campbell@citrix.com>
Wed, 25 Feb 2015 13:39:48 +0000 (13:39 +0000)
committerIan Campbell <ian.campbell@citrix.com>
Tue, 3 Mar 2015 11:26:24 +0000 (11:26 +0000)
commitf0ffd6032f679ec4b9a39d526cdbcdaf692e2f03
tree11036164193b02516e095a44f2de11ce925b4ef2
parentf3d370b016cfc82dbda0a800a1c9382a2bcc30f8
netif.h: describe request/response structures in terms of binary layout

In RFC style, rather than relying on the implicit assumptions of a
particular C ABI.

I have also confirmed, using the Python gdb extension technique in
[0], that the struct offsets (in a Linux binary at least) are the same
as described here.

I took the opportunity to also confirm that x86_32, x86_64, arm32 and
arm64 are all the same.

This highlighted that struct netif_rx_request was missing some
explicit padding, which is added here.

Lastly, fixup some struct names to allow the generated docs to
properly hyperlink, mainly by adding the _t to type names where
appropriate, but also s/netif_tx_extra/netif_extra_info_t/.

[0] http://stackoverflow.com/questions/9788679/how-to-get-the-relative-adress-of-a-field-in-a-structure-dump-c

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Cc: Roger Pau Monné <roger.pau@citrix.com>
Acked-by: Wei Liu <wei.liu2@citrix.com>
xen/include/public/io/netif.h